MMEMory...    Related Topics

The MMEMory system provides mass storage capabilities for the analyzer.  

Internal and external mass storage

The mass storage of the analyzer may be internal or external. The internal mass storage device can be any section of the internal hard disk (mapped to drive C:\). The external mass storage device can be a floppy disk inserted into the drive at the front panel of the instrument, which is mapped to drive a:\ (see MMEMory:MSIS), a USB memory stick connected to one of the USB ports (mapped to any free drive letter) or a network connection.

File and directory names

The <file_name> and <directory_name> parameters are strings. Some commands use a fixed directory; for others the <file_name> can contain the complete path including the drive name and all subdirectories, e.g. 'C:\TEMP\TRASH\test.txt' for the file named test.txt in the TEMP\TRASH subdirectory of the internal hard disk drive C:\. If no complete path is specified, the file location is relative to the current directory (queried with MMEMory:CDIRectory?). The file name itself may contain the period as a separator for extensions.

File and directory names can be chosen according to Windows™ conventions; the restrictions placed on file names known from DOS systems do not apply. All letters and numbers are allowed, as well as the special characters "_", "^", "$", "~", "!", "#", "%", "&", "-", "{", "}", "(", ")", "@" and "`". Reserved file names are CON, AUX, COM1, ..., COM4, LPT1, ..., LPT3, NUL and PRN.

The use of wildcards ? and * is not allowed.  

 

Command tree: MMEMory

:AKAL

:FACTory

:CONVersion

:CATalog?

:ALL?

:CDIRectory

:COPY

:DATA

:DELete

:CORRection

:LOAD

:CKIT

:CMAP

:CORRection

:RESolve

:LIMit

:SEGMent

:STATe?

:TRACe

:VNETworks<Ch>

:BALanced

:DEEMbedding<Log_pt>

:EMBeddin<Log_pt>

:SENDed

:DEEMbeddin<Ph_pt>

:EMBedding<Ph_pt>

:MDIRectory

:MOVE

:NAME

:RDIRectory

:STORe

:CKIT

:CMAP

:CORRection

:LIMit

:MARKer

:STATe

:TRACe

MMEMory:AKAL:FACTory:CONVersion '<directory_name>'

Converts the calibration data of the standards in the active calibration unit (SYSTem:COMMunicate:RDEVice:AKAL:ADDRess) to Touchstone format and copies it to the specified directory.

'<directory_name>'

String parameter to specify the directory.

*RST value

–

 

SCPI, Command Types

Device-specific, command or query (returns the current directory).

 

Example:

MMEM:AKAL:FACTory:CONVersion 'C:\AKAL\Touchstone'

Convert and copy the calibration data of the standards to the specified directory.

 

 

MMEMory:CATalog? [<directory_name>]

Returns the contents of the current or of a specified directory.

Use MMEMory:CATalog:ALL? to query the contents of the current directory and all subdirectories.

'<directory_name>'

String parameter to specify the directory. If the directory is omitted, the command queries the contents of the current directory, to be queried  with MMEMory:CDIRectory?

 

Response

Directory information in the following format:

<used_size>,<free_disk_space> {,<file_name>,,<file_size>}
 

The first two numeric parameters denote the total amount of storage currently used in the directory and the total amount of storage available, both expressed in bytes. All files are returned with their file name and their size in bytes.

*RST value

–

 

SCPI, Command Types

Confirmed, query only.

 

Example:

MMEM:CAT?
Response:  2056878, 809734144, zvb_quickstart.pdf, , 2056878,

 

 

MMEMory:CATalog:ALL? [<directory_name>]

Returns the contents of the current or of a specified directory and all subdirectories.

Use MMEMory:CATalog? to query the contents of the current directory.

'<directory_name>'

String parameter to specify the directory. If the directory is omitted, the command queries the contents of the current directory, to be queried  with MMEMory:CDIRectory?

 

Response

Directory information in the following format:

Directory of <Dir_name>, <used_size>, <free_disk_space> {, <Subdir>, <DIR>,}{,<file_name>,,<file_size>},
Directory of <Subdir_name_1>, <used_size>,<free_disk_space> {, <Subdir>, <DIR>,}{,<file_name>,,<file_size>},
Directory of <Subdir_name_2>, <used_size>,<free_disk_space> ...
 

The first line is omitted if the current directory contains no subdirectories. The following lines are analogous to the output of MMEMory:CATalog?.

*RST value

–

 

SCPI, Command Types

Confirmed, query only.

 

Example:

MMEM:CAT:ALL?

Response:  Directory of C:\Rohde&Schwarz\Nwa\DOC\, 2056878, 809734144, zvb_quickstart.pdf, , 2056878,

 

 

MMEMory:CDIRectory '<directory_name>'

Changes the default directory for mass memory storage.

'<directory_name>'

String parameter to specify the directory.

*RST value

– (A *RST does not change the current directory)

 

SCPI, Command Types

Confirmed, command or query (returns the current directory).

 

Example:

MMEM:CDIR 'C:\Documents and Settings\NetworkService\Application Data'

Change to the specified directory.

 

 

MMEMory:COPY '<file_source>','<file_destination>'

Copies an existing file to a new file.

'<file_source>', '<file_destination>'

String parameters to specify the name of the file to be copied and the name of the new file.

*RST value

–

 

SCPI, Command Types

Confirmed, no query.

 

Example:

MMEM:COPY 'C:\USER\DATA\SETUP.CFG','A:'

Copy file Setup.cfg in directory C:\USER\DATA to the external storage medium, mapped to drive A:\.

 

 

MMEMory:DATA '<file_name>', <data>

Loads <data> into the file <file_name>.

'<file_name>'

String parameter to specify the name of the file.

 

<data>

Data in 488.2 block data format. The delimiter EOI must be selected to achieve correct data transfer.

*RST value

–

 

SCPI, Command Types

Confirmed, with query. The query form is MMEMory:DATA? <file_name> with the response being the associated <data> in block format.

 

Example:

MMEM:DATA? 'C:\TEMP\TEST01.HCP'

Query the block data contained in file TEST01.HCP.

 

 

MMEMory:DELete '<file_name>'

Removes a file from the specified directory.

'<file_name>'

String parameter to specify the name and directory of the file to be removed.

 

*RST value

–

 

SCPI, Command Types

Confirmed, no query.  

 

Example:

MMEM:DEL 'C:\TEMP\TEST01.HCP'

Remove TEST01.HCP from the current directory.

 

 

MMEMory:DELete:CORRection <file_name>'

Deletes a system error correction data set stored in the cal pool (cal group file).  

'<file_name>'

String parameter to specify the name of the cal group file to be deleted. Cal group files must have the extension *.cal. The directory path must not be specified; the analyzer always uses the default cal pool directory C:\Rohde&Schwarz\NWA\Calibration\Data.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

See  MMEMory:LOAD:CORRection

 

 

MMEMory:LOAD:CKIT '<file_name>'

Loads cal kit data from a specified NWA cal kit file.

'<file_name>'

String parameter to specify the name and directory of the cal kit file to be loaded. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.  

Note: The loaded file must be a NWA-specific cal kit file with the extension *.calkit. ZVR cal kit files can be imported using the [SENSe<Ch>:]CORRection:CKIT:INSTall command. Agilent cal kit files can be imported manually and converted into *.calkit files.  

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

MMEM:LOAD:CKIT 'C:\Rohde&Schwarz\NWA\Calibration\Kits\New_kit.calkit'

Load the previously created cal kit file New_kit.calkit from the default cal kit directory.

... :MMEM:STOR:CKIT 'Newkit', 'C:\Rohde&Schwarz\NWA\Calibration\Kits\New_kit.calkit'

Store the data for the user-defined cal kit Newkit and overwrite the cal kit file New_kit.calkit.

 

 

MMEMory:LOAD:CKIT:SDATa
'<conn_name>', '<ckit_name>', MMTHrough | MFTHrough | FFTHrough | MMLine | MFLine | FFLine | MMATten | MFATten | FFATten | MMSNetwork | MFSNetwork | FFSNetwork | MOPen | FOPen | MSHort | FSHort | MOSHort | FOSHort | MREFlect | FREFlect | MMTCh | FMTCh | MSMatch | FSMatch, '<stdlabel_name>', '<file_name>' [,<port1_no>][,<port2_no>]

Loads cal kit data for a specific connector type, cal kit, and calibration standard from a specified Touchstone file, assigning a label for the cal data. A restriction on the port assignment may be defined in addition.

'<conn_name>'

String parameters containing the name of the connector type.

 

'<ckit_name>'

String parameters containing the name of a calibration kit available on the analyzer.

 

Parameters

Standard type; for a description refer to the table of standard types.

 

'<stdlabel_name>'

String parameter defining a label for the cal kit data. An empty string means that no label is defined.

 

'<file_name>'

String parameter to specify the name and directory of the Touchstone file to be loaded. A *.s1p file must be used for one-port standards, a *.s2p file for two-port standards. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.  

 

<port1_no>, <port2_no>

Port assignment: One port number for one-port standards, two port number for two-port standards. If the port numbers are omitted, the cal kit data is valid for all ports.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

MMEM:LOAD:CKIT:SDAT 'N 50 Ohm','Default Kit',MOPEN,'Test data','test.s1p',1

Load the file Test.s1p from the current directory in order to define the properties of an Open (m) standard in the cal kit named Default Kit for the N 50 W connector type. Assign the label Test data and specify that the data standard data is only valid for port no. 1.  

 

 

Connector and cal kit naming conventions

Connector and calibration kit names must be entered as string parameters. The strings contain the connector and cal kit names used in the Calibration Kits dialog; a W in the name must be replaced by 'Ohm', e.g.:

MMEMory:LOAD:CMAP '<file_name>'

Loads a color scheme from a specified NWA color scheme file.

'<file_name>'

String parameter to specify the name and directory of the cal kit file to be loaded. The default extension (manual control) for color scheme files is *.ColorScheme, although other extensions are allowed.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

MMEM:LOAD:CMAP 'C:\Rohde&Schwarz\NWA\ColorSchemes\Test.ColorScheme'

Load the previously created color scheme file Test.ColorScheme from the default color scheme directory.

DISP:CMAP13:RGB 1,0,0; DISP:CMAP14:RGB 0,1,0

Color the first trace red, the second trace green.

MMEM:STOR:CMAP 'C:\Rohde&Schwarz\NWA\ColorSchemes\Test.ColorScheme'

Store the data for the user-defined cal kit Newkit and overwrite the cal kit file New_kit.calkit.

 

 

MMEMory:LOAD:CORRection <Ch>,'<file_name>'

Applies a system error correction data set stored in the cal pool (cal group file) to channel no. <Ch>.  

<Ch>

Channel number of an existing channel

 

<file_name>

String parameter to specify the name of the cal group file to be loaded. Cal group files must have the extension *.cal. The directory path must not be specified; the analyzer always uses the default cal pool directory C:\Rohde&Schwarz\NWA\Calibration\Data.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

MMEM:STOR:CORR 1,'Calgroup1.cal'

Copy the current correction data set of channel 1 to a cal group file Calgroup1.cal.

CONF:CHAN2:STAT ON; :MMEM:LOAD:CORR 2,'Calgroup1.cal'

Apply the stored correction data to channel 2.

MMEM:LOAD:CORR:RES 2,'Calgroup1.cal'

Undo the previous action: Resolve the link, causing channel 2 to use its previous correction data.

MMEM:DEL:CORR 'Calgroup1.cal'

Delete the created cal group file.

 

 

MMEMory:LOAD:CORRection:RESolve <Ch>[,'<file_name>']

Resolves the link between channel <Ch> and the correction data set (cal group file) so that the channel uses its previous correction data.

<Ch>

Channel number

 

'<file_name>'

Optional string parameter to specify the name of the cal group file. Cal group files must have the extension *.cal. The directory path must not be specified.
If there is no link between <Ch> and the specified file, the command has no effect. If no file is specified, the command resolves any link between <Ch> and an arbitrary cal group file.  

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

See MMEMory:LOAD:CORRection

 

 

MMEMory:LOAD:LIMit '<trc_name>','<file_name>'

Loads a limit line definition from a specified file and assigns it to a trace with a specified name. Limit lines are created using the CALCulte<Chn>:LIMit... commands.

'<trc_name>'

Name of an existing trace in the active setup (string parameter). The imported limit line is assigned to this trace, irrespective of the trace information in the limit line file.

 

'<file_name>'

String parameter to specify the name and directory of the limit line file to be loaded. The default extension (manual control) for limit line files is *.limit, although other extensions are allowed. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

 

Assume that the current setup contains two traces named Trc1 and Trc2, respectively, and that limit lines have been defined for Trc1.

MMEM:STOR:LIM 'TRC1', 'C:\Rohde&Schwarz\NWA\LIMitLines\Lim_Trc1.limit'

Store the limit line definition of Trc1 to a limit line file.

MMEM:LOAD:LIM 'TRC2', 'C:\Rohde&Schwarz\NWA\LIMitLines\Lim_Trc1.limit'

Load the previously created limit line file and assign the limit lines to Trc2.

 

 

MMEMory:LOAD:SEGMent <Ch>,'<file_name>'

Loads a sweep segment definition from a specified file and assigns it to a specified channel. Sweep segments are defined using the [SENSe<Ch>:]SEGMent<Seg>... commands.

<Ch>

Channel number.

 

'<file_name>'

String parameter to specify the name and directory of the sweep segment file to be loaded. The default extension (manual control) for sweep segment files is *.seglist, although other extensions are allowed. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

 

Assume that the current setup contains two channels numbered 1 and 2, respectively, and that sweep segments have been defined for channel no. 1.

:MMEM:STOR:SEGM 1, 'C:\Rohde&Schwarz\NWA\SweepSegments\Seg_Ch1.seglist'

Store the sweep segment definition of channel 1 to a sweep segment file.

MMEM:LOAD:SEGM 2, 'C:\Rohde&Schwarz\NWA\SweepSegments\Seg_Ch1.seglist'

Load the previously created sweep segment file and use the sweep segments for channel 2.

 

  

MMEMory:LOAD:STATe <numeric_value>,'<file_name>'

Loads configuration data from a specified setup file and sets the analyzer to the corresponding instrument state.

<numeric_value>

1 (the <numeric_value> is used for compatibility with the SCPI standard but is ignored).

 

<file_name>

String parameter to specify the name and directory of the setup file to be loaded. The default extension (manual control) for setup files is *.zvx, although other extensions are allowed. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

 

 

*RST value

–

 

SCPI, Command Types

Confirmed, no query.  

 

Example:

MMEM:STOR:STAT 1,'C:\Rohde&Schwarz\NWA\RecallSets\Setup_0413.zvx'

Store the current setup configuration in the file Setup_0413.ZVX in the default directory for setup files.

MMEM:LOAD:STAT 1,'C:\Rohde&Schwarz\NWA\RecallSets\Setup_0413.zvx'

Load the settings stored in Setup_0413.ZVX.

 

 

MMEMory:LOAD:TRACe '<trc_name>','<file_name>'[,'<parameter_name>']

Loads trace data from a specified trace file and assigns it to a trace with a specified name. Traces are created using the CALCulte<Ch>:PARameter:SDEFine... command.

'<trc_name>'

Name of an existing data trace in the active setup (string parameter). The trace data is loaded into a memory trace associated with the specified data trace. If one or more memory traces are already associated with the specified data trace, the last generated memory trace is overwritten.

 

'<file_name>'

String parameter to specify the name and directory of the trace file to be loaded. Several file formats for trace files are supported. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

 

'<parameter_name>'

Optional parameter for imported Touchstone files for more than one port (*.s2p, *.s3p, *.s4p); denotes the imported S-parameter (S11, S12, ...). If nothing is specified, the first trace in the specified is imported.

*RST value

–

 

SCPI, Command Types

Confirmed, no query.  

 

Example:

 

Assume that the current setup contains a trace named Trc1.

:MMEM:STOR:TRAC 'TRC1', 'C:\Rohde&Schwarz\NWA\Traces\Trc1.s1p'

Store the current trace data of Trc1 to a trace file.

MMEM:LOAD:LIM 'TRC2', 'C:\Rohde&Schwarz\NWA\Traces\Trc1.s1p'

Load the previously created trace file and create a memory trace assigned to Trc2.

 

 

MMEMory:LOAD:VNETworks<Ch>:BALanced:DEEMbedding<Log_pt> '<file_name>', PMAin | PSECondary

Loads data from a specified Touchstone file defining the characteristics of the current deembedded balanced port circuit model. A balanced port circuit model involving file import must be selected before using the command.

<Ch>

Channel number

 

<Log_pt>

Logical port number

'<file_name>'

String parameter to specify the name and directory of the loaded Touchstone file. The balanced port circuit models STSL | STSC | SLST | SCST require two 2-port (*.s2p) files, to be assigned to the different ports PMAin and PSECondary; the FIMPort model requires a single 4-port (*.s4p) file but no additional port assignment.  

If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

 

Parameters

Port assignment for two 2-port (*.s2p) files:
PMAin – Port 1
PSECondary – Port 2

The ports must be specified for the import of 2-port (*.s2p) files; they must be omitted for 4-port (*.s4p) files.

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

*RST; SOUR:LPOR1 1,2; LPOR2 3,4

Define a balanced port configuration.

CALC:TRAN:VNET:BAL:DEEM:TND STSL

Select the Serial .s2p data, shunt L circuit model.

MMEM:LOAD:VNET:BAL:DEEM2 'C:\Rohde&Schwarz\NWA\VNETWORKS\Test.s2p', PMA

Load a Touchstone file and assign it to logical port no. 2.

 

 

MMEMory:LOAD:VNETworks<Ch>:BALanced:EMBedding<Log_pt> '<file_name>', PMAin | PSECondary

Loads data from a specified Touchstone file defining the characteristics of the current embedded balanced port circuit model. A balanced port circuit model involving file import must be selected before using the command.

<Ch>

Channel number

 

<Log_pt>

Logical port number

 

'<file_name>'

String parameter to specify the name and directory of the loaded Touchstone file. The balanced port circuit models STSL | STSC | SLST | SCST require two 2-port (*.s2p) files, to be assigned to the different ports PMAin and PSECondary; the FIMPort model requires a single 4-port (*.s4p) file but no additional port assignment.  

If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

 

Parameters

Port assignment for two 2-port (*.s2p) files:
PMAin – Port 1
PSECondary – Port 2

The ports must be specified for the import of 2-port (*.s2p) files; they must be omitted for 4-port (*.s4p) files.

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

*RST; SOUR:LPOR1 1,2; LPOR2 3,4

Define a balanced port configuration.

CALC:TRAN:VNET:BAL:EMB:TND STSL

Select the Serial .s2p data, shunt L circuit model.

MMEM:LOAD:VNET:BAL:EMB2 'C:\Rohde&Schwarz\NWA\VNETWORKS\Test.s2p', PMA

Load a Touchstone file and assign it to logical port no. 2.

 

 

MMEMory:LOAD:VNETworks<Ch>:SENDed:DEEMbedding<Ph_pt> '<file_name>'

Loads data from a specified two-port (*.sp2) Touchstone file defining the characteristics of the current deembedded single ended port circuit model. The single ended port circuit model involving file import (FIMPort) must be selected before using the command.

<Ch>

Channel number.

 

<Ph_pt>

Physical port number

'<file_name>'

String parameter to specify the name and directory of the loaded Touchstone file. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

CALC:TRAN:VNET:SEND:DEEM:TND FIMP

Select the Serial .s2p data, shunt L circuit model.

MMEM:LOAD:VNET:SEND:DEEM2 'C:\Rohde&Schwarz\NWA\VNETWORKS\Test.s2p'

Load a Touchstone file and assign it to the physical port no. 2.

 

 

MMEMory:LOAD:VNETworks<Ch>:SENDed:EMBedding<Ph_pt> '<file_name>'

Loads data from a specified two-port (*.sp2) Touchstone file defining the characteristics of the current embedded single ended port circuit model. The single ended port circuit model involving file import (FIMPort) must be selected before using the command.

<Ch>

Channel number.

 

<Ph_pt>

 

'<file_name>'

String parameter to specify the name and directory of the loaded Touchstone file. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

CALC:TRAN:VNET:SEND:EMB:TND FIMP

Select the Serial .s2p data, shunt L circuit model.

MMEM:LOAD:VNET:SEND:EMB2 'C:\Rohde&Schwarz\NWA\VNETWORKS\Test.s2p'

Load a Touchstone file and assign it to the physical port no. 2.

 

 

MMEMory:MDIRectory '<directory_name>'

Creates a new directory for mass memory storage.

'<directory_name>'

String parameter to specify the directory.

*RST value

–

 

SCPI, Command Types

Device-specific, no query.

 

Example:

MMEM:MDIR 'C:\Documents and Settings\NetworkService\Application Data'

Create the specified directory.

 

 

MMEMory:MOVE '<file_source>','<file_destination>'

Copies an existing file to a new file.

'<file_source>', '<file_destination>'

String parameters to specify the name of the file to be copied and the name of the new file.

*RST value

–

 

SCPI, Command Types

Confirmed, no query.

 

Example:

MMEM:COPY 'C:\USER\DATA\SETUP.CFG','A:'

Copy file Setup.cfg in directory C:\USER\DATA to the external storage medium, mapped to drive A:\.

 

 

MMEMory:NAME '<file_name>'

Defines a name for a file which can be used to store the printer output. The file is created when it is selected as a printer destination (HCOPy:DESTination 'MMEM').

'<file_name>'

String parameter to specify the file name. The supported file formats are *.wmf, *.ewmf, *.bmp, *.png; see command HCOPy:DEVice:LANGuage. The specified directory must exist, otherwise no file can be generated. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

'Hardcopy'

 

SCPI, Command Types

Device-specific, with query.

 

Example:

MMEM:NAME 'C:\Screenshots\PLOT1.BMP'

Define a printer file name, to be stored in the existing directory C:\Screenshots (without creating the file).

HCOP:DEST 'MMEM'; HCOP

Select 'Print to file' and create the printer file specified before.

 

 

MMEMory:RDIRectory '<directory_name>'

Removes an existing directory from the mass memory storage system.

'<directory_name>'

String parameter to specify the directory.

*RST value

–

 

SCPI, Command Types

Device-specific, no query.

 

Example:

MMEM:RDIR 'C:\Documents and Settings\NetworkService\Application Data'

Removes the specified directory.

 

 

MMEMory:STORe:CKIT '<kit_name>', '<file_name>'

Stores the data of a calibration kit to a specified file.

'<kit_name>'

Name of a user-defined calibration kit available on the analyzer. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

Note: Predefined or dummy kits can neither be modified nor be stored.

 

'<file_name>'

String parameter to specify the name and directory of the cal kit file to be created. The file is a NWA-specific cal kit file with the extension *.calkit.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

MMEM:LOAD:CKIT 'C:\Rohde&Schwarz\NWA\Calibration\Kits\New_kit.calkit'

Load the previously created cal kit file New_kit.calkit from the default cal kit directory.

... :MMEMory:STORe:CKIT 'Newkit', 'C:\Rohde&Schwarz\NWA\Calibration\Kits\New_kit.calkit'

Store the data for the user-defined cal kit Newkit and overwrite the cal kit file New_kit.calkit.

 

 

MMEMory:STORe:CMAP '<file_name>'

Stores a color scheme to a specified NWA color scheme file.

'<file_name>'

String parameter to specify the name and directory of the cal kit file to be created. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?. The default extension (manual control) for color scheme files is *.ColorScheme, although other extensions are allowed.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

See MMEMory:LOAD:CMAP

 

 

MMEMory:STORe:CORRection <Ch>,'<file_name>'

Copies the correction data of channel <Ch> to the cal pool, generating a new correction data file (cal group). The file has the extension *.calkit and is stored in the C:\Rohde&Schwarz\NWA\Calibration\Data directory.

<Ch>

Channel number

 

'<file_name>'

String parameter to specify the name of the created cal group file. The directory path must not be specified; the analyzer always uses the default cal pool directory C:\Rohde&Schwarz\NWA\Calibration\Data.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

See MMEMory:LOAD:CORRection

 

 

MMEMory:STORe:LIMit '<trc_name>', '<file_name>'

Saves the limit lines associated to a specified trace to a limit line file. Limit lines are created using the CALCulte<Chn>:LIMit... commands.

'<trc_name>'

Name of an existing trace in the active setup (string parameter) for which a limit line definition exists.

 

'<file_name>'

String parameter to specify the name and directory of the created limit line file. The default extension (manual control) for limit line files is *.limit, although other extensions are allowed. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

See MMEMory:LOAD:LIMit.

 

 

MMEMory:STORe:MARKer '<file_name>'

Saves the values of all markers to a ASCII file.  

'<file_name>'

String parameter to specify the name and directory of the created ASCII file. The default extension (manual control) for marker files is *.txt, although other extensions are allowed. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?. An example for the file contents is given below.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

*RST

Reset the analyzer, creating the default trace no. 1 in channel no. 1.

CALC:MARK ON; MARK:X 1GHz  

Create marker no. 1 and place it to 1 GHz.  

CALC:MARK2 ON; MARK2:X 2GHz  

Create a second marker and place it to 2 GHz.    

MMEM:STOR:MARK 'Marker.txt'   

Store the marker values to an ASCII file. The file contains both marker values:
  

 

 

MMEMory:STORe:SEGMent <Ch>, '<file_name>'

Saves the sweep segment definition of a specified channel to a sweep segment file. Sweep segments are defined using the [SENSe<Ch>:]SEGMent<Seg>... commands.

<Ch>

Channel number.

 

'<file_name>'

String parameter to specify the name and directory of the created sweep segment file. The default extension (manual control) for sweep segment files is *.seglist, although other extensions are allowed. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

 

*RST value

–

 

SCPI, Command Types

Device-specific, no query.  

 

Example:

See MMEMory:LOAD:SEGMent.

 

  

MMEMory:STORe:STATe <numeric_value>,'<file_name>'

Stores the configuration data of the current setup to a specified setup file.

MMEMory:STORe:STATe renames the current setup, appending a .zvx extension. See example for MMEMory:LOAD:STATe.

<numeric_value>

1 (the <numeric_value> is used for compatibility with the SCPI standard but is ignored).

 

'<file_name>'

String parameter to specify the name and directory of the created setup file. The default extension (manual control) for setup files is *.zvx, although other extensions are allowed. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

 

*RST value

–

 

SCPI, Command Types

Confirmed, no query.  

 

Example:

See MMEMory:LOAD:STATe.

 

 

MMEMory:STORe:TRACe '<trc_name>','<file_name>'[,UNFormatted | FORMatted]

Stores the trace data of a specified trace to a trace file. Traces are created using the CALCulte<Ch>:PARameter:SDEFine... command.

*.s<n>p Touchstone files (<n> = 2, 3,, 4) are intended for a complete set of <n>-port S-parameters. Data export fails if the active channel does not contain the full set of <n>2 traces. If the necessary trace are available, '<trc_name>' can be the name of any of the traces.

'<trc_name>'

Name of an existing data trace in the active setup (string parameter).

 

'<file_name>'

String parameter to specify the name and directory of the created trace file. Several file formats for trace files are supported. If no path is specified the analyzer uses the C:\Rohde&Schwarz\NWA\Traces directory.

 

Optional parameters

UNFormatted – Specifies unformatted (complex) data export
FORMatted – Specifies formatted data export

If the optional parameter is omitted the command stores unformatted data.

 

*RST value

– (the default export format is UNFormatted)

 

SCPI, Command Types

Confirmed, no query.  

 

Example:

See MMEMory:LOAD:TRACe.